Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/playground/lib/main.dart`:
- Around line 215-222: The conditional rendering block checking if _connected &&
_status != 'connected' is incorrect because _status is set to 'connected ✓'
elsewhere (e.g., where connection success is assigned), causing the block to
always render; update the comparison to match the actual status value (either
compare to the same exact string used when setting _status like 'connected ✓' or
use a stable enum/constant for statuses) or change the check to something like
!_status.startsWith('connected') to avoid duplicate status output; adjust
references in the widget where _status is set and where the conditional uses
_connected and _status to ensure both use the same canonical status
representation (consider introducing a STATUS_CONNECTED constant or using
startsWith('connected')).

In `@apps/playground/test/widget_test.dart`:
- Around line 59-62: The test uses a fixed delay via tester.pump(const
Duration(milliseconds: 50)), which is flaky; replace that fixed-duration pump
with a deterministic wait such as await tester.pumpAndSettle() (or
tester.pumpAndSettle(timeout: ...) if needed) after the
tester.tap(find.text('Trigger Code Action')) so the test waits for
animations/async work to finish reliably instead of relying on a 50ms sleep.

In `@docs/TLS.md`:
- Around line 3-5: Update the documentation to use the published Flutter package
name: replace references to "formbricks" when referring to the Flutter SDK with
the correct package name "formbricks_flutter" (e.g., change the phrase
"formbricks Flutter SDK" to "formbricks_flutter package" or "formbricks_flutter
Flutter SDK"). Search for occurrences of "formbricks" in this doc (including the
opening sentence and any install/integration sections) and ensure they
consistently refer to "formbricks_flutter" when describing the Flutter package
to avoid confusion.

In `@Makefile`:
- Around line 79-86: The Makefile’s format targets are non-deterministic and not
CI-enforced: update the format-docs and format-check targets and the format
invocation so markdown formatting is pinned and validated; change the format
target to call $(MAKE) format-docs, change format-docs from "npx -y prettier
--write \"**/*.md\"" to a pinned invocation like "npx prettier@2.8.8 --write
\"**/*.md\"" (choose your locked version), and add markdown validation to
format-check by running the pinned prettier with a check flag (e.g., "npx
prettier@2.8.8 --check \"**/*.md\"") so CI will fail on drift; reference the
Makefile targets format, format-docs, and format-check when making these edits.

In `@packages/formbricks_flutter/CHANGELOG.md`:
- Around line 1-4: Update the CHANGELOG.md to reflect the actual shipped SDK
behavior by either adding a new version entry (e.g., "## 0.0.2" or "Unreleased")
or revising the existing "## 0.0.1" entry: remove or update the phrase about "No
SDK behavior yet" and add concise bullet points describing the implemented
features such as survey tracking and WebView delivery (mentioning the
`welcome()` API only if its behavior changed), so the changelog accurately
documents the PR's functionality.

In `@packages/formbricks_flutter/lib/src/common/setup.dart`:
- Around line 65-73: The cooldown logic currently checks any cached error state
(`existing` / `existing.status`) regardless of which setup target was used, so
fixed credentials can still be blocked; update the check and the persistence to
scope cooldown to the specific setup target (e.g., include `appUrl` and
`workspaceId` or a derived `targetKey` in the stored status). Concretely: when
persisting the status (the code around where status is saved), attach the target
identifiers to the stored record; when reading `existing` before returning
`SetupCooldownError` (the block using `existing.status`, `expiresAt`, and
`isNowExpired`), verify the stored target matches the current
`appUrl`/`workspaceId` (or `targetKey`) and only enforce the cooldown if it
matches; otherwise ignore the stale status and proceed with setup. Ensure
`SetupCooldownError(retryAt: expiresAt)` remains unchanged but is only returned
for matching targets.

In `@packages/formbricks_flutter/lib/src/common/utils.dart`:
- Around line 29-31: Normalize the survey language code before comparing by
lowercasing the language code as well as the alias: in utils.dart where the
matching occurs (the condition using l.language.code and l.language.alias
compared to the local variable lower), change the comparison to use
l.language.code?.toLowerCase() (null-safe) and keep
l.language.alias?.toLowerCase(), so getLanguageCode (and the selection logic
that sets selected) will match regardless of case.

In `@packages/formbricks_flutter/lib/src/survey/action.dart`:
- Around line 75-80: The NetworkError created in action.dart (returned via
Result.err) incorrectly uses HTTP 500 for an offline condition; update the
offline path in the code that constructs NetworkError (the Result.err(...) call)
to avoid using 500 — set status to 0 or null (or add an explicit offline/nonHttp
boolean on NetworkError) and leave the URL/Uri.tryParse(...) as-is; ensure
callers that inspect NetworkError.status treat 0/null (or the new offline flag)
as “no network” rather than a server error.
- Around line 109-113: The catch block in action.dart currently maps every
exception to NetworkError; instead, update the handler in the function using
Logger.error / Result.err to preserve typed errors: if the caught exception is a
FormbricksError return Result.err(e) (preserving its type and message),
otherwise wrap unknown exceptions in a distinct internal error type (e.g.,
InternalError or a new OperationError) that includes the original exception and
stack/context, and log the full exception when calling Logger.error; do not
collapse all failures into NetworkError.

In `@packages/formbricks_flutter/lib/src/survey/survey_store.dart`:
- Around line 25-30: The guard in setSurvey only compares survey.id so updates
that change survey content but keep the same id are dropped; update setSurvey
(the method) to compare the whole survey object instead of just id (e.g., check
_notifier.value != survey) or remove the id-only guard and always assign
_notifier.value = survey so listeners receive refreshed payloads; ensure you use
TSurvey equality (override ==/hashCode on the model if needed) when using object
inequality.

In `@packages/formbricks_flutter/lib/src/widgets/default_webview_host.dart`:
- Around line 120-136: The unawaited(_hardenAndLoad(_controller, widget.html))
call can surface unhandled async errors from the WebViewController operations;
modify _hardenAndLoad so it catches PlatformException/Exception around its
platform checks and calls (platform.setAllowFileAccess, setAllowContentAccess,
clearCache, clearLocalStorage, loadHtmlString) and handles failures (log via
debugPrint or the project's logger and return gracefully) so no exception
escapes as an unhandled future; alternatively, keep the caller but change the
unawaited invocation to unawaited(_hardenAndLoad(...).catchError((e, s) => /*
log/report */)) to ensure all errors from _hardenAndLoad are observed and
handled.

In `@packages/formbricks_flutter/lib/src/widgets/formbricks_widget.dart`:
- Around line 124-136: The _setup() method currently ignores the Result returned
by Formbricks.setup; change it to capture the Result (e.g., var res = await
Formbricks.setup(...)) and handle the Err case: if res.isErr (or matches Err),
log the error detail via Logger.error/Logger.debug including the err value, set
the widget state to a failed/initialized flag (or rethrow the error) to prevent
silent silent not_setup behavior, and only proceed when res.isOk; update
references to _setup, Formbricks.setup, and Logger.debug accordingly.

In `@packages/formbricks_flutter/lib/src/widgets/webview_navigation.dart`:
- Around line 33-42: The origin comparison in isAllowedWebViewNavigation uses
_origin to stringify the URI and treats explicit default ports (e.g., :443) as
different from omitted ports; update _origin to normalize default ports by
omitting the port when it equals the scheme's default (80 for http, 443 for
https) so that URIs like https://host and https://host:443 produce the same
origin; modify the _origin helper (referenced by isAllowedWebViewNavigation) to
compute an effective port and only include the :port suffix when a non-default
port is present.

In `@packages/formbricks_flutter/test/widgets/formbricks_widget_test.dart`:
- Around line 80-83: Replace the timing-sensitive manual delays by using
deterministic widget-test settling: where you currently call tester.runAsync(()
=> Future<void>.delayed(...)) followed by tester.pump(), change to
tester.pumpAndSettle() (or a pumpUntil-condition) to wait for frames and
microtasks to complete; update each occurrence of
tester.runAsync/Future<void>.delayed + tester.pump (including the other similar
blocks using tester.runAsync) to use tester.pumpAndSettle() so tests are stable
on slow CI.

In `@packages/formbricks_flutter/test/widgets/survey_webview_test.dart`:
- Around line 199-203: Replace the brittle fixed 50ms sleeps inside the
tester.runAsync blocks (where host.onEvent!(const DisplayCreatedEvent()) is
called and then you await Future.delayed(...)) with a deterministic polling wait
that repeatedly calls the side‑effect check (_storedUserData() or other expected
predicate) until it returns the expected result or a timeout elapses; implement
a small helper (e.g., waitForCondition or pumpUntil) used by the tests to poll
_storedUserData() and/or the storedData predicate with a short interval and a
sensible timeout, then swap the Future.delayed calls in the blocks around
host.onEvent!/DisplayCreatedEvent (and the same pattern at the other
occurrences) to await this helper so tests become deterministic and CI‑stable.